Skip to content

Conversation

@aignas
Copy link
Collaborator

@aignas aignas commented Nov 22, 2025

The arm64 macs have been in the wild for a while and it makes more sense
to test against that platform instead of the Intel macs that very few
people in our user-base are using.

At the same time clarify the supported platforms.

@aignas aignas requested a review from rickeylev as a code owner November 22, 2025 09:04
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @aignas, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes our continuous integration setup by migrating all macOS-based CI jobs to utilize Apple Silicon (ARM64) architecture. This change aligns our testing environment with the more prevalent hardware in our user base and clarifies the official support tiers for different macOS platforms in our documentation.

Highlights

  • CI Platform Update: All macOS CI jobs have been switched from running on Intel-based Macs (macos) to Apple Silicon-based Macs (macos_arm64).
  • Documentation Clarification: The docs/support.md file has been updated to reflect the new platform tiering, promoting osx_arm64 to Tier 0 (primary CI platform) and demoting osx_x86_64 to Tier 1.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly switches the macOS CI jobs from Intel-based machines to ARM64, which is a great update to align with the current developer ecosystem. The changes in .bazelci/presubmit.yml to use macos_arm64 and the corresponding update in docs/support.md to move osx_arm64 to a Tier 0 supported platform are consistent with the goal. I've left one comment regarding an inconsistency in CI task naming for future improvement.

name: "Default: Debian"
platform: debian11
macos:
macos_arm64:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This task key was updated to macos_arm64, which is great for clarity. However, other macOS task keys in this file were not renamed (e.g., integration_test_bzlmod_macos), creating an inconsistency. For better maintainability, consider renaming all macOS task keys to reflect the architecture change in a follow-up PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant